@github-actions crossbow submit test-r-linux-valgrind

https://issues.apache.org/jira/browse/ARROW-17252

⚠️ Ticket has not been started in JIRA, please click 'Start Progress'.

Revision: d38781f

Submitted crossbow builds: ursacomputing/crossbow @ actions-c87d0167a9

Task	Status
test-r-linux-valgrind

@github-actions crossbow submit test-r-linux-valgrind

Revision: aa429ab

Submitted crossbow builds: ursacomputing/crossbow @ actions-66d788420f

Task	Status
test-r-linux-valgrind

@github-actions crossbow submit test-r-linux-valgrind

Revision: ca0e250

Submitted crossbow builds: ursacomputing/crossbow @ actions-74e7027351

Task	Status
test-r-linux-valgrind

@github-actions crossbow submit test-r-linux-valgrind

Revision: fcbd862

Submitted crossbow builds: ursacomputing/crossbow @ actions-17da8ef45a

Task	Status
test-r-linux-valgrind

@github-actions crossbow submit test-r-linux-valgrind

Revision: 6d48ad5

Submitted crossbow builds: ursacomputing/crossbow @ actions-57dbd50f21

Task	Status
test-r-linux-valgrind

@github-actions crossbow submit test-r-linux-valgrind

Revision: ac58c2d

Submitted crossbow builds: ursacomputing/crossbow @ actions-be43d8f311

Task	Status
test-r-linux-valgrind

@github-actions crossbow submit test-r-linux-valgrind

Revision: e38cb2c

Submitted crossbow builds: ursacomputing/crossbow @ actions-f396285a0a

Task	Status
test-r-linux-valgrind

@github-actions crossbow submit test-r-linux-valgrind

Revision: 7717616

Submitted crossbow builds: ursacomputing/crossbow @ actions-8c1b73e0ba

Task	Status
test-r-linux-valgrind

@github-actions crossbow submit test-r-linux-valgrind

Revision: 123d8bd

Submitted crossbow builds: ursacomputing/crossbow @ actions-d76d1348a1

Task	Status
test-r-linux-valgrind

This PR was useful to run crossbow jobs to see if the known leak caused by shutting down the IO thread pool before a plan finishes is a possible cause of the valgrind errors. This does seem to be the case...we observe intermittent leaks that occasionally are a direct leak of an ExecPlan. Closing in favour of #13773, since that version is a more direct rollback of a change that caused the errors to start.